Skip to content

Conversation

jonathanc-n
Copy link
Contributor

Which issue does this PR close?

Rationale for this change

What changes are included in this PR?

Are these changes tested?

Are there any user-facing changes?

@github-actions github-actions bot added core Core DataFusion crate execution Related to the execution crate labels Oct 9, 2025

/// Deregister the store previously registered with the same key. Returns the
/// deregistered store if it existed.
fn deregister_store(&self, url: &Url) -> Result<Arc<dyn ObjectStore>>;
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is breaking, we can add a label. I'm thinking maybe we can have a default return value and remove it in another version but I don't know what would be a good default return value (I was thinking of just erroring).

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you mean that giving it a default value and letting users be aware of the new API in the next release, then removing the default value in the next release after next?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, but I am very open to doing it another way if there is a more standard way to deal with this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

core Core DataFusion crate execution Related to the execution crate

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Support unregister_store for datafusion

2 participants